System for establishing a shared media session for one or more client devices

ABSTRACT

A system is provided for establishing a shared media session for client devices that receives event data and media corresponding to a shared media session and previous shared media sessions from a recording client device communicably coupled to a distributed communication network. A persistent record of the event data and media is generated until the shared media session is terminated by at least one of a first client device or by abandonment of the distributed communication network by the first client device and by second client devices. A new disparate live media output stream is generated with multiple distinct channels based on augmentation of a disparate live media output stream in the shared media session. The augmentation is based on an interaction from a user on actions in the shared media session.

CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE

This Patent Application is a Continuation of U.S. Pat. No. 11,038,932,issued on Jul. 15, 2021, which claims priority to, and the benefit fromU.S. Provisional Application Ser. No. 62/699,131.

Each of the above referenced patent applications is hereby incorporatedherein by reference in its entirety.

FIELD OF TECHNOLOGY

Certain embodiments of the disclosure relate to a television contentpackaging and distribution system. More specifically, certainembodiments of the disclosure relate to a method and system forestablishing a shared media session for one or more client devices.

BACKGROUND

Recent advancements in the field of television content packaging anddistribution systems have led to a massive development of numeroustechnologies and broadcasting platforms that are revolutionizing the wayclient devices access and playout media content. Usually, broadcastingplatforms refer to the types of networks that are used to deliver themedia content to the consumers. Currently, the broadcasting platforms,such as analog terrestrial broadcast, digital terrestrial broadcast,direct-to-home satellite broadcast, cable, Internet Protocol (IP), andover-the-top television (OTT), compete and strive to increase theirappeal by gaining and retaining the audience viewing the media content.

Modern streaming protocols, such as HTTP Live Streaming (HLS) andDynamic Adaptive Streaming over HTTP (DASH), are implemented to supportstreaming of various live content services, such as through DIRECTVNOW℠, SLING TV℠ and PLAYSTATION™ VUE, to the client devices. Due todissemination of such modern streaming protocols in the television,radio, and broadcasting sector, it is evident that the success ofbroadcasting will be dependent on the ability of the network provider togain access to the content that consumers demand, and to differentiatetheir offering from that of incumbent broadcasters or find breakthroughmodes of media content delivery.

Existing systems that publish live output streams in a content deliverysystem may require a scheduler or a network operator to create achannel. Accordingly, the amount of control a user may excerpt toinfluence what programming and non-programming content is shown may bevery limited.

Given the trend toward media content distribution, there is required atelevision content packaging and distribution system that may leverage asystem, which provides to the capability for a user, for example, aviewer, to have a more direct impact on the what programming andnon-programming content that is shown. This may provide the networkprovider with the ability to not only provide new channel offerings in acost-effective manner but also provide enhanced, intelligent, andpersonalized viewer experience to increase their appeal in order to gaina wider audience and retain the audience viewing the media content.

Further limitations and disadvantages of conventional and traditionalapproaches will become apparent to one of skill in the art, throughcomparison of such systems with some aspects of the present disclosureas set forth in the remainder of the present application with referenceto the drawings.

BRIEF SUMMARY OF THE DISCLOSURE

Systems and/or methods are provided for establishing a shared mediasession for one or more client devices, substantially as shown in and/ordescribed in connection with at least one of the figures, as set forthmore completely in the claims.

These and other advantages, aspects and novel features of the presentdisclosure, as well as details of an illustrated embodiment thereof,will be more fully understood from the following description anddrawings.

BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS

FIGS. 1A and 1B are block diagrams that illustrate an exemplary systemfor establishing a shared media session for one or more client devices,in accordance with an exemplary embodiment of the disclosure.

FIG. 1C is a block diagram that illustrates an exemplary recordingclient device, in accordance with an exemplary embodiment of thedisclosure.

FIG. 2 illustrates segmentation of live input streams and pre-encodedmedia assets for a programming schedule for establishing a shared mediasession for one or more client devices by the shared media sessionsystem of FIGS. 1A and 1B, in accordance with an exemplary embodiment ofthe disclosure.

FIG. 3A depicts a first flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

FIG. 3B depicts a second flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

FIG. 3C depicts a third flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

FIG. 3D depicts a fourth flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

FIG. 4 is a conceptual diagram illustrating an example of a hardwareimplementation for the shared media session system employing aprocessing system for establishing a shared media session for one ormore client devices, in accordance with an exemplary embodiment of thedisclosure.

DETAILED DESCRIPTION OF THE DISCLOSURE

Certain embodiments of the disclosure may be found in a method andsystem for establishing a shared media session for one or more clientdevices. Various embodiments of the disclosure provide a method andsystem that not only provide live channel offerings in a cost-effectivemanner but also provide enhanced, intelligent, and personalized viewerexperience to increase their appeal by retaining the audience viewingthe media content.

In accordance with various embodiments of the disclosure, a system isprovided for establishing a shared media session for one or more clientdevices. One or more processors in the system may be configured toestablish a shared media session. The shared media session may include adisparate live media output stream scheduled by a first client device tostart at a defined timestamp. The disparate live media output stream maybe played back on one of the first client device or a plurality ofclient devices that comprises the first client device and one or moresecond client devices. The plurality of client devices may join theshared media session through the distributed communication network.During the shared media session, event data and media among theplurality of client devices in the shared media session may besynchronized through the distributed communication network based on oneor more criteria. The one or more processors in the shared media sessionsystem may be further configured to receive the event data and mediacorresponding to the shared media session and previous shared mediasessions from the recording client device communicably coupled to thedistributed communication network. The one or more processors in theshared media session system may be further configured to generate apersistent record of received event data and media corresponding to theshared media session and previous shared media sessions until the sharedmedia session is terminated by at least one of the first client deviceor by abandonment of the distributed communication network by the firstclient device and by the one or more second client devices.

FIGS. 1A and 1B are block diagrams that illustrate an exemplary systemfor establishing a shared media session for one or more client devices,in accordance with an exemplary embodiment of the disclosure. Referringto FIG. 1A, the system 100, comprises a media packaging and distributionsystem 102 that is communicatively coupled to published data sources 104a, . . . , 104 n, Ad decisioning servers 106 a, . . . , 106 n, via anetwork 108 and/or other programmatic means. There are shown a pluralityof client devices 110 comprising a first client device 110 a and one ormore second client devices 110 b, . . . , 110 n that are communicativelycoupled with each other to form a distributed communication network 112,which is further coupled to the network 108. The media packaging anddistribution system 102 may comprise a dynamic ad/content insertionsystem (DACIS) 103, a shared media session system 105, a contentpackaging and distribution system (CPDS) 107, and an external storagesystem 109. There are also shown source devices 118 communicativelycoupled to the media packaging and distribution system 102 through thenetwork 108. An external data source 120 is also provided, which iscommunicatively coupled to the media packaging and distribution system102 through the network 108.

The media packaging and distribution system 102 may comprise suitablelogic, circuitry, and interfaces that may be configured to execute codethat handles media content comprising audio, video, images, metadata,manifests, and/or other data (embedded and/or externally referenced).The media content may include a video, an audio, a combination of audioand video presentations, and/or embedded or externally referencedmetadata, a combination of multiple-audio, multiple-video, and/orembedded or externally referenced metadata. Accordingly, the mediapackaging and distribution system 102 establishes a shared media sessionfor the plurality of client devices 110.

In this regard, the media packaging and distribution system 102 mayprovide video programming services to viewers, usually for asubscription fee (such as pay television). The media packaging anddistribution system 102 also handles distribution, for example,multicasting, unicasting, broadcasting, streaming, for one or morechannels to be viewed on one or more of the plurality of client devices110.

The media packaging and distribution system 102 may be operated by anentity related to handling or distribution of media content, forexample, a broadcast provider or operator, or a network provider ornetwork operator. The entity related to handling or distribution ofmedia content may also be referred to as a content owner, a distributor,a syndicator, a re-distributor, a content aggregator, a search,discovery, or cataloging service provider, or any other entity activelyor passively involved with the distribution, cataloging, or referencingof complete or partial presentations of media content. Throughout thisdocument, the terms broadcast provider or broadcast operator, andnetwork provider or network operator may be utilized to refer to theentity related to handling or distribution of media content,interchangeably. The broadcast provider may handle a single channel or aplurality of channels, or one or more networks. The broadcast providermay be configured to distribute content via one or more platforms, forexample, traditional over-the-air broadcast channels, radio, cabletelevision networks, satellite communication networks, the Internet,and/or other content delivery networks (CDNs). In this regard, thebroadcast provider may be configured to execute code that communicateslinear video feeds (also referred to as a network television feed orbroadcast feed) to the media packaging and distribution system 102. In abroadcast chain, the broadcast provider may receive actual content, forexample, from a production studio, in one or more source formats.Examples of the one or more source formats may include, but are notlimited to a tape file, or a live feed that may be further converted toa serial digital interface (SDI) video interface and/or on ahigh-definition SDI (HD-SDI) video interface for processing and playout.The broadcast provider may further process the content, such asinsertion of graphics, closed captions, preparation of programmingschedule, insertion of triggers, and the like, and final delivery by abroadcasting apparatus. The communicated linear video feed and theplayout schedule may correspond to a channel, such as CNN channel thatis broadcast to the media packaging and distribution system 102, via acommunication network. The linear video feed may be broadcasted as amulti-program transport stream (MPTS) (also referred to as a live videofeed) to the media packaging and distribution system 102, via thenetwork 108. The broadcast provider may be owned by (or associated to) abroadcast provider or operator, a network provider or operator, or acontent provider or operator.

The media packaging and distribution system 102 may receive the MPTS,which includes the signaling content and metadata, from the broadcastprovider based on, for example, current society of cabletelecommunication engineers (SCTE) standards (SCTE-35 and SCTE-224) tocontrol web and regional blackouts, network end of day switching, andadvertisement insertion. For example, the media packaging anddistribution system 102 may be signaled for various blackout types within-band SCTE-35 message. Further, the media packaging and distributionsystem 102 may receive program metadata that specifies certain events oroperations, such as, for example, when to blackout shows. Examples oflegacy distribution system that may be benefitted from the mediapackaging and distribution system 102 may include direct-broadcastsatellite (DBS) providers, cable television (CATV) systems, and otherwireline video providers and competitive local exchange carriers (CLECs)using, for example, IPTV.

The DACIS 103 may be an optional system in the media packaging anddistribution system 102, and may comprise suitable logic, circuitry, andinterfaces that may be configured to construct and deliver targetedand/or personalized media streams. The DACIS 103 may leverage one-to-onescale of traditional server-side ad insertion systems to support customprogramming content choices and not just targeted non-programmingcontent. For example when the user selects to join a live stream, acontent decisioning system could determine that, instead of joining thelive stream for the last few minutes of a program, the user shouldinstead be shown content more relevant to the next program e.g. show apersonalized set of basketball highlights and ads to a user who likelyjoined the stream to watch the basketball game that is coming on next—donot join the live stream until the previous program ends and the gamestarts.

The DACIS 103 may be further configured to, via a programming scheduleor tag indicator in a disparate live media output stream manifest, benotified of one or more content graphical treatment opportunities withinthe media content. The DACIS 103 may be further configured to makerequired non-programing content calls on behalf of the plurality ofclient devices 110. Accordingly, the DACIS 103 may provide the pluralityof client devices 110 with information needed to execute the graphicaltreatment graphical content via a secure out-of-band channel between theDACIS 103 and the plurality of client devices 110. In accordance with anembodiment, the DACIS 103 may be configured to include not showingnon-programming content that a user of a client device may elected toskip or rated poorly in an earlier non-programming content break.Further, the DACIS 103 may enable the user to skip non-programmingcontent as the user interacted with a previous non-programming contentor made a purchase and the advertiser elected to sponsor the remainderof the programming content.

In accordance with an embodiment, the DACIS 103 may be configured toprovide seamless failover between redundant disparate live media outputstreams for large events, thus improving reliability. In certaininstances, some of the plurality of client devices 110 may support aprimary and backup disparate live media output streams and are able tofail between them. In other instances, others of the plurality of clientdevices 110 may not support the primary and backup disparate live mediaoutput streams. In such instances, the client devices have to crash andthen try to join an alternative disparate live media output stream. Forsuch client devices, the DACIS 103 may be configured to monitor both theprimary and backup disparate live media output streams, and if there isa failure, write the alternative disparate live media output stream intothe disparate live media output stream manifest. In accordance with anembodiment, the DACIS 103 may be configured to receive required mediacontent from the CPDS 107.

Each of the plurality of published data sources 104 a, . . . , 104 n maybe coupled to one or more television networks and may comprise suitablelogic, circuitry, and interfaces that may be configured to execute codethat provides actual audiences for programs that were distributed. Asillustrated in FIG. 1A, the plurality of published data sources 104 a, .. . , 104 n are coupled to the media packaging and distribution system102 via the network 108 and configured to monitor audience drift to oraway from a tuned channel airing a live media output stream. Theplurality of published data sources 104 a, . . . , 104 n may provideactual audiences for programs to an indexing and storage system. Anexemplary published data source may be Nielsen. Nielsen has thecapability to determine when a viewer watches the same set of mediaitems, for example, advertisements and/or promotional content, inprogramming data, such as an episode, in a live video feed within 3 daysof original airing, and provide Nielsen “C3” credit. Another exemplarypublished data source may be a published database that provides ratingsfor a media item, such as gross rating point (GRP). The GRP isadvertising or promotion impact measure for each advertising and/orpromotional campaigns, known in the art. Other exemplary published datasources may include direct/indirect access to other public or privatedata sources (persistent or ephemeral) through programmatic means.

The shared media session system 105 may comprise suitable logic,circuitry, and interfaces that may be configured to execute a code tomanage and establish shared media sessions with the plurality of clientdevices 110. The shared media session may correspond to duration ofmedia playback with the plurality of client devices 110 acting asparticipants, whom may be exchanging data and other media as a form ofinteraction. The shared media session system 105 may be furtherconfigured to facilitate participants of a shared media session withconstructing a peer-to-peer network, such as the distributedcommunication network 112, between the participants. The shared mediasession system 105 may be further configured to facilitate one or moreparticipants to select a disparate live media output stream from a listof available disparate live media output streams. The participant maycorrespond to a user taking part in the shared media session, andconsuming the media of the shared media session. The participant mayalso act as a client on the peer-to-peer network associated with theshared media session.

In accordance with an embodiment, the shared media session system 105may be configured to receive list of available media content from theDACIS 103. In accordance with another embodiment, the shared mediasession system 105 may be configured to receive list of available mediacontent from the CPDS 107. In accordance with yet another embodiment,the shared media session system 105 may be configured to receive a listof available media content from one of the plurality of client devices110. For example, the first client device 110 a may be configured torequest the shared media session system 105 for a specific Youtube®video for further sharing.

The Ad decisioning servers 106 a, . . . , 106 n may comprise suitablelogic, circuitry, and interfaces that may be configured to implement atleast an advertisement decisioning component that may be used during areal-time content or advertisement placement activity, for exampleduring dynamic ad insertion. For example, commercial or non-commercialadvertisements may be dynamically inserted within program segments ofthe live input streams by the Ad decisioning servers 106 a, . . . , 106n based on the upcoming indicator detected by the media player or thenon-programming content proxy server (not shown). The detected indicatormay be, such as an inbound trigger, a signaling point, and/or a signalin a pre-encoded media asset and/or a live input stream. The Addecisioning servers 106 a, . . . , 106 n may receive a request forretrieval of non-programming content, for example, ads, from anon-programming content proxy server (not shown). Specifically, the Addecisioning servers 106 a, . . . , 106 n may receive the request fromone or more of the plurality of client devices 110, via thenon-programming content proxy server (not shown). The request may bereceived when one or more indicators and/or pre-encoded place holdercontent segment for a scheduled duration of one or more non-programmingcontent breaks. The scheduled durations of one or more non-programmingcontent breaks may be defined by a received programming schedule, andare encountered in the disparate live media output stream manifestduring media content playout by media players at the one or more of theplurality of client devices 110.

For requests that are received from the plurality of client devices 110,based on corresponding disparate live media output stream manifests, theAd decisioning servers 106 a, . . . , 106 n may identity theopportunities for the real-time content or advertisement placementactivity. In this regard, as the advertisement decisioning component ofthe Ad decisioning servers 106 a, . . . , 106 n is implemented in aclient device, such as one or more of the plurality of client devices110, the Ad decisioning servers 106 a, . . . , 106 n may identifyreal-time content or advertisement placement opportunity for dynamic adinsertion. For example, commercial or non-commercial advertisements maybe dynamically inserted within program segments of a media feed based onthe detected indicator, such as upcoming inbound trigger, signalingpoint, and/or signal, in the disparate live media output stream manifestby the Ad decisioning servers 106 a, . . . , 106 n when the addecisioning component is implemented in the client device. In variousembodiments, the advertisement decisioning component of the Addecisioning servers 106 a, . . . , 106 n may be configured to determinewhich advertisements, graphical treatment graphics and presentationinformation to serve to the plurality of client devices 110 based onstream ID, a program ID, a geographical location, time, and anypreferences associated with an individual consumer or an advertisementID specified by the disparate live media output stream manifest.

The CPDS 107 may comprise suitable logic, circuitry, and interfaces thatmay be configured to index programming content, which is prepared forusage. The CPDS 107 may further define metadata detailing various facetsof the programming and/or non-programing content including duration,known locations and opportunities for programing and/or non-programingcontent insertion/replacement.

The network 108 may be any kind of network, or a combination of variousnetworks, and it is shown illustrating the communication that may occurbetween the Ad decisioning servers 106 a, . . . , 106 n and the mediapackaging and distribution system 102. For example, the network 108 maycomprise one or more of a cable television network, the Internet, asatellite communication network, a wide area network (WAN), a mediumarea network (MAN), and a local area network (LAN). Although a network108 is shown, the disclosure is not limited in this regard; accordingly,other exemplary modes may comprise uni-directional or bi-directionaldistribution, such as packet-radio, satellite. Furthermore, the network108 is an exemplary embodiment of a distribution system.

The external storage system 109 may comprise suitable logic, circuitry,and interfaces that may be configured to execute a code to implement apersistent storage of past shared media sessions, containing sharedmedia session event data, audio, and video.

The plurality of client devices 110 may include client devices 110 a, .. . , 110 n that may refer to end-user devices or consumption deviceswhere the content is played to be consumed by a user. Each client devicemay correspond to a node on the distributed communication network 112established for a given shared media session, where a client device mayparticipate. The number of impressions of a media item, such as anadvertisement and/or promotional media, on such plurality of clientdevices 110 determines the advertising impact or promotion impact andnumber of actual audiences achieved during campaigns. Examples of theplurality of client devices 110 may include, but are not limited to,connected TVs, connected TV with paired and/or connected devices (e.g.,HDMI sticks, tablets), personal computer, smartphone, tablet, OTTset-top, or hybrid set-top, and second screen devices such assmartphones, tablets, game consoles, personal computers, set-top boxes,and embedded devices. The plurality of client devices 110 may furtherinclude process/system that may process the output for any means,regardless of the capability or intent to decode for media presentation,and on which the consumer may launch a web page, a web application, or aweb service to view media content.

The distributed communication network 112 may comprise suitable logic,circuitry, and interfaces that may be configured to replicate apeer-to-peer network constructed by the participants, such as theplurality of client devices 110, in a given shared media session. Thedistributed communication network 112 may be used to exchange eventdata, video, and audio between peers to enable interaction between theparticipants themselves, and the participants and the media.

The recording client device 114 may comprise suitable logic, circuitry,and interfaces that may be configured to act as a client that connectsto the distributed communication network 112 of the shared mediasession. The recording client device 114 may further observe or recordevent data, video, and audio exchanged by the remaining peers on thedistributed communication network 112 such that all the recorded eventsmay be maintained in the external storage system 109. Such recordedevents may be packaged in one or more formats to be provided from theCPDS 107 as another media content to be viewed or searched. After theshared media session has ended, the recording client device 114 mayupload the recording of the shared media session to the external storagesystem 109.

The source devices 118 may comprise suitable logic, circuitry, andinterfaces that may be configured to communicate a live media feed orlive input streams of a channel, such as an existing channel, to themedia packaging and distribution system 102. In accordance with anembodiment, the live input streams of the channel may correspond to abroadcast feed. The source device 118 may be communicatively coupled tothe network 108.

The external data source 120 may comprise suitable logic, circuitry, andinterfaces that may be configured to execute code that handles retrievaland storage of audience data that corresponds to subscribers of theplurality of client devices 110. The audience data may includedemographics data, audience targeting data, trending data, device typedata, device platform data, and content recognition-based data, such asautomatic content recognition (ACR)-based data. The trending datacomprises information on what's trending in the social networks (orplatforms), such as Twitter®, Facebook®, and the like. The trending dataalso comprises information on what's trending based on socialengagement, such as number of likes or votes to a particular media item,or number of people watching a particular media item. The trending datamay indicate an aggregate interest level of a number of users in thesocial networks for a particular media item. For example, a thousand ormore shares, or likes by a number of users may indicate a highly popularmedia item.

The content delivery system 122, as described in FIG. 1B, may comprisesuitable logic, circuitry, and interfaces that may be configured todistribute media content to the plurality of client devices 110.Generally, the term “content,” “metadata,” “media,” and similar wordsare used interchangeably to refer to any type of media—audio, videos,datacasts, music, text, images, graphics, articles, photos, photogalleries, video galleries, infographics, maps, polls, guestbiographies, tweets or other social media, blog posts, and/or the like.The content delivery system 122 may be configured to provide a pluralityof disparate live media output streams to the plurality of clientdevices 110, via a transport stream, segmented streaming, progressivedownload, or any other modes of distributing a multimedia presentation,such as via an over-the-air content delivery/distribution network, alinear content delivery/distribution network, a cable contentdelivery/distribution network, a satellite content delivery/distributionnetwork, an Internet Protocol (IP) based content delivery/distributionnetwork, and/or the like.

FIG. 1C is a block diagram that illustrates an exemplary client deviceand recording client device, in accordance with an exemplary embodimentof the disclosure. Referring to FIG. 1C, a client device, such as thefirst client device 110 a, may comprise a graphics engine 124, a mediaplayer 126, and a first peer-to-peer module 128. The recording clientdevice 114 may comprise a second peer-to-peer module 130, an eventmetadata indexer 132, a media recorder 134, and a file uploader 136.

The graphics engine 124 may comprise suitable logic, circuitry, andinterfaces that may be configured to perform the graphics dataprocessing required to illustrate a 2D or 3D image, text, video, orother media onto a client device corresponding to a received disparatelive media output stream manifest. Such image may include one or moreobjects having visually apparent dimensions in relation to two or threedefined axes based on hardware and software configuration of the clientdevice. Typically, the graphics engine 124 comprises of a geometryprocessing unit, a rasterization unit, and a special function register(SFR).

The media player 126 may comprise suitable logic, circuitry, andinterfaces that may be configured to process disparate live media outputstream manifests comprising media segments of live input streams and/orpre-encoded media assets. Accordingly, the media player 126 may beconfigured to generate corresponding disparate live media outputstreams. Such disparate live media output streams may comprise audio,video, images, or a combination thereof that may correspond to livemedia input streams and/or pre-encoded media assets. The audio mayinclude an external media, an audio recorded from a microphone, or anapplication-specific audio resource. Video may include an externalmedia, a video recorded from peer camera, or application-specific videoresources (for example, interactive animations). The media player 126may be further configured to communicate the disparate live media outputstream to the graphics engine 124 for rendering media content.

The first peer-to-peer module 128 may comprise suitable logic,circuitry, and interfaces that may be configured to establish apeer-to-peer connection between the client devices from the plurality ofclient devices 110. The second peer-to-peer module 130 may comprisesuitable logic, circuitry, and interfaces that may be configured to joina peer-to-peer connection between the recording client device 114 andclient devices from the plurality of client devices 110.

The event metadata indexer 132 may comprise suitable logic, circuitry,and interfaces that may be configured to index metadata associated withan event, such as a user interaction with media, a user interaction withanother user, broadcast notifications of a network state of the user,and/or broadcast notifications of an application state of the user.Examples of the user interaction with media may include, but are notlimited to, pausing video for all users andrewinding/fast-forwarding/seeking media for all users. Examples of thebroadcast notifications of the network state of the user may include,but are not limited to, a connected state, a disconnected state, or asending data state. Examples of the broadcast notifications of theapplication state of the user may include, but are not limited to, amuted audio, an invoked interactive element, an interactive elementinvocation completion, and/or a change in user applicationconfiguration.

The media recorder 134 may comprise suitable logic, circuitry, andinterfaces that may be configured to record event data, and media, suchas video and audio, exchanged by the remaining peers, such as theplurality of client devices 110, during the shared media session.

The file uploader 136 may comprise suitable logic, circuitry, andinterfaces that may be configured to upload the recording of the sharedmedia session to the external storage system 109, such as the recordedclient sessions database.

In operation, the shared media session system 105 in the media packagingand distribution system 102 may be configured to generate a shared mediasession for a disparate live media output stream requested (or selected)by a user associated with a client device, for example, the first clientdevice 110 a. In accordance with an embodiment, the shared media sessionsystem 105 may be configured to provide a list of available mediacontent comprising live input streams and/or pre-encoded media assetsfor selection to the user.

The shared media session system 105 may further define a contentidentifier for the shared media session. Based on the contentidentifier, one or more of the plurality of client devices 110 may beconfigured to request data associated with the recorded shared mediasession. The shared media session may be defined to have at least anumber of participants, a selection of media content based on which adisparate live media output stream manifest is generated, a first flagthat indicates the shared media session is discoverable by the one ormore second client devices 110 b, . . . , 110 n via, and a second flagthat indicates the shared media session is to be recorded. Eachparticipant, such as one of the plurality of client devices 110 mayinteract with the playback of the disparate live media output stream. Asdescribed above, the media content may be selected by the userassociated with the first client device 110 a from a list of existingand referenced media content provided by the one or more processors, orsubmitted by the user from an external source.

In accordance with various embodiments, the user associated with thefirst client device 110 a may initiate an establishment of asingle-participant or a multi-participant shared media session with theshared media session system 105. The user may schedule the disparatelive media output stream and initiate the playback of the disparate livemedia output stream. In case of single-participant shared media session,the shared media session may not have more than one participant, forexample the first client device 110 a. Further, in case ofsingle-participant shared media session, the disparate live media outputstream may comprise media segments of a live input stream or apre-encoded media asset. However, in case of multi-participant sharedmedia session, the shared media session may have more than oneparticipant, for example the plurality of client devices 110. Further,in case of multi-participant shared media session, the disparate livemedia output stream may comprise media segments of one or more liveinput streams and/or one or more pre-encoded media assets.

In accordance with an embodiment when the shared media session is asingle-participant shared media session, the user associated with thefirst client device 110 a may be configured to initiate a playback ofdisparate live media output stream selection, via the media player 126,based on scheduling of the disparate live media output stream to becreated. In accordance with an embodiment, the shared media session maybe flagged for recording, as indicated by the second flag, either duringshared media session creation or after shared media session initiation.The first client device 110 a may be configured to establish thedistributed communication network 112, such as a peer-to-peerconnection. The first client device 110 a may communicate a clientidentifier and an IP address to the shared media session system 105. Therecording client device 114 may be configured to join the distributedcommunication network 112 established by the first client device 110 a,via the second peer-to-peer module 130. The recording client device 114may be configured to record event data and media exchanges thatoriginate from the first client device 110 a during playback. Suchrecordings may not include the disparate live media output streamselected for playback during the shared media session. Each event dataand media exchange may have a playhead time of playback of the disparatelive media output stream, and a real-time of the event. The event dataand the media exchanges may then be synchronized with the playback ofthe disparate live media output stream.

In accordance with various embodiments, the user may choose to pause,seek, rewind, or fast-forward as the window of the disparate live mediaoutput stream allows. Thereafter, the user may choose to terminate theshared media session. When the first client device 110 a abandons thedistributed communication network 112, the recording client device 114may cease the recording of the event data and the media exchanges. Inaccordance with an embodiment, the recording client device 114 maygenerate an alert for the shared media session system 105 to close theshared media session.

In accordance with an embodiment when shared media session is amulti-participant shared media session, the participants, such as thesecond client devices 110 b, . . . , 110 n, may be configured todiscover and join the shared media session, via the correspondingpeer-to-peer modules, similar to the first peer-to-peer module 128. Insuch case, the shared media session may be advertised explicitly andselected by the first client device 110 a via an invitation or a shareduniversal resource locator, via an external advertisement service via auniversal resource locator or an identifier, or within context of agroup of shared media sessions discovered within the shared mediasession system 105.

When multiple participants join the shared media session, a firstparticipant, for example the first client device 110 a, may establishthe distributed communication network 112 and communicates the clientidentifier and IP address to the shared media session system 105 whereit is stored. Thereafter, other participants, for example the secondclient devices 110 b, . . . , 110 n in the shared media session maydiscover the new client identifier from the shared media session system105. The distributed communication network 112 may be establisheddirectly between the participants where client identifier of eachparticipant may be used to identify and share data between variousparticipants, such as the plurality of client devices 110. Mediaexchanged between the participants, corresponding to the shared mediasession and previous shared media sessions from the recording clientdevice 114, may include, but are limited to audio and video. Audio mayinclude, for example, external media, audio recorded from a microphone,or application-specific audio resources. Video may include, for example,external media, video recorded from peer camera, or application-specificvideo resources (for example, interactive animations). Further, eventdata corresponding to the shared media session and previous shared mediasessions may include, but are not be limited to a user interaction withthe disparate live media output stream to pause video for all users orrewind/fast-forward/seek disparate live media output stream for allusers, a user interaction with another user, a broadcast notificationsof network state of the user, or a broadcast notifications ofapplication state of the user. The shared media session system 105 mayobserve the event data and the media exchanges on the shared mediasession by use of the distributed communication network 112. Based onthe received event data and the media exchanges, the shared mediasession system 105 may generate the persistent records. The persistentrecords may include a persistent audio exchanged between participants onthe distributed communication network 112, persistent video exchangedbetween participants on the distributed communication network 112,persistent event data exchanged between participants on the distributedcommunication network 112, time of event data, audio, and video inaccordance with real time, and time of event data, audio, and video datain accordance with time of the disparate live media output stream. Inaccordance with an embodiment, the recording of the shared media sessionmay be coordinated with the start of shared media session and accordingto number of participants in the distributed communication network 112.

In accordance with an embodiment, the file uploader 136 in the recordingclient device 114 may upload the persistent record to the externalstorage system 109. In such cases, the event data, audio, and video maybe used to recreate the shared media session in the future. Further, thepersistent record may be referenced from the external storage system 109and further distributed through a distribution system, such as the CPDS107.

In accordance with an embodiment, the shared media session may bescheduled within the shared media session system 105 to start at a givendate and time. The date and time may correspond to a live event.Further, an ability of a participant to join or not join the sharedmedia session may coordinate disparate live media output stream with thescheduled date and time.

In accordance with an embodiment, a participant in the distributedcommunication network 112 may initiate the playback of the disparatelive media output stream. For example, a client device of the pluralityof client devices 110 may be configured to initiate the playback of thedisparate live media output stream. The playback of the disparate livemedia output stream may be synchronized across the participants. Thesynchronization may be performed using streaming media and control flowprotocols (for example Real Time Streaming Protocol (RTSP)/Real-timeTransport Protocol (RTP)), using a hybrid of two or more streaming mediaand control flow protocols (for example RTSP/RTP with TS segments fromHLS), using the synchronizing client device to send playhead timerelative to the calculated offset of a given time of a participant,constraining a live window of playback of the disparate live mediaoutput stream and the size of the media segments such that thevariability of different playback positions is limited to an acceptedvalue, or a combination thereof.

In accordance with an embodiment, the event data may be synchronized toall participants across the distributed communication network 112. Theevent data may contain a combination of real-time and media playheadtime to maintain event sequence. Further, the events may haveapplication-specific actions that may be executed, such as, but notlimited to interactivity between participants, updating playback stateof the disparate live media output stream, changing playback state ofthe disparate live media output stream, changing application state,and/or addition or removal of participants to or from the distributedcommunication network 112.

The persistent records may be further distributed and/or promoted fromthe external storage system 109. In accordance with an embodiment, thepersistent records, having been synchronized with the playback of thedisparate live media output stream, may then be transcoded anddistributed as a new media asset.

In accordance with an embodiment, when the plurality of client devices110 abandon the distributed communication network 112, the recordingclient device 114 may be configured to cease the recording of the eventdata and media exchanges. Thereafter, the recording client device 114may generate an alert for the shared media session system 105 to closethe shared media session.

In accordance with another embodiment, the shared media session system105 in the media packaging and distribution system 102 a may beconfigured to generate a new disparate live media output stream byaugmenting existing disparate live media output stream. The augmentationof the existing disparate live media output stream may be based onadditional data and/or media (such as audio or video), having resultedfrom the persisted record of the shared media session. The new disparatelive media output stream may have multiple distinct audio channels,resulting from a participant audio interaction, such as voice, and aparticipant-invoked application audio. The new disparate live mediaoutput stream may further have multiplexed audio, that may comprise aparticipant audio interaction, such as voice, a participant-invokedapplication audio, or an original media audio.

For example, while watching a basketball game as a disparate live mediaoutput stream during a shared media session, one or more users providecomments on one or more actions of players at one or more timestamps.Thus, the resulting persistent record of the shared media session maycomprise an audio of the one or more users commenting in relation to thedisparate live media output stream, such as the basketball game, at theone or more timestamps. The CPDS 107 may be configured to retrieve thepersistent record comprising the audio that was recorded andconsequently augment to the existing disparate live media output streamand operate as a new disparate live media output stream.

The recording client device 114 may be configured to record the eventdata and media exchanges between client devices from the plurality ofclient devices 110 during playback of the existing disparate live mediaoutput stream. The persistent record may exclude the existing disparatelive media output stream selected for the shared media session playback.Each event data and media exchange may include playhead time of theplayback of the existing disparate live media output stream, andreal-time of event. Further, the event data and media exchange may besynchronized with the playback of the existing disparate live mediaoutput stream in the shared media session. Such persistent record of theevent data and media exchanges may be synchronized with the playback ofthe existing disparate live media output stream of the shared mediasession and transcoded and distributed as the new disparate live mediaoutput stream. As described above, the recording client device 114 maybe configured to communicate the generated persistent record to theexternal storage system 109 for further distribution and promotion. Inaccordance with an embodiment, a shared media session may be recreatedat a future time based on the event data and media in the persistentrecord. In accordance with an embodiment, the CPDS 107 may be configuredto distribute the persistent record, retrieved from the external storagesystem 109, to the plurality of client devices 110 in the distributedcommunication network 112 via the content delivery system 122. Inaccordance with an embodiment, the CPDS 107 may be configured totranscode from the existing, persistent and stored version to a newformat. Consequently, persistent records, comprising recorded event dataand media exchanges, having been synchronized with playback of theexisting disparate live media output stream in the shared media session,may be transcoded and distributed as a new disparate live media outputstream. Upon the plurality of client devices 110 abandoning thedistributed communication network 112, the recording client device 114may be configured to cease the recording. Further, the recording clientdevice 114 may alert the shared media session system 105 to close (orterminate) the shared media session.

FIG. 2 illustrates segmentation of live input streams and pre-encodedmedia assets for a programming schedule for establishing a shared mediasession for one or more client devices by the shared media sessionsystem 105 of FIGS. 1A and 1B, in accordance with an exemplaryembodiment of the disclosure. Referring to the exemplary arrangement ofFIG. 2 , there is shown a first live input stream 202, a firstpre-encoded media asset 204, and a second live input stream 206. Thereis also shown a targeted first non-programming content 208 placed afterthe first live input stream 202, and a customized first programmingcontent 210 placed after the first pre-encoded media asset 204 by theDACIS 103. The first live input stream 202 may be segmented into a firstset of video segments 202 a, 202 b, 202 c, . . . , 202 n. Similarly, thefirst pre-encoded media asset 204 and the second live input stream 206may also be segmented into second set of video segments 204 a, 204 b,204 c, . . . , 204 n, and third set of video segments 206 a, 206 b, 206c, . . . , 206 n respectively. By way of example, the segmentation maybe executed by a segmenting system (not shown) during a preparationstage of the media assets. In accordance with an embodiment, thesegments of the first set of video segments 202 a, 202 b, 202 c, . . . ,202 n, the second set of video segments 204 a, 204 b, 204 c, . . . , 204n, and third set of video segments 206 a, 206 b, 206 c, . . . , 206 n,may be segmented into consistent length, for example, 10 secondssegments. It may be advantageous to have a consistent and smaller filesize of segments to be able to quickly push to the content deliverysystem 122, and also for quick downloading by a media player at theend-user side, such as on the plurality of client devices 110.

It is to be understood by those skilled in the art that various changesmay be made and segments of different file sizes (or length) may be usedwithout departure from the scope of the present disclosure. Further, itshould be recognized by one skilled in the art that other streamingprotocols may require a different processing of media content. Thus, thescope of the disclosure should not be limited to the processing orpreparation of media content to allow delivery using different deliverymethods, streaming protocols, or distribution system, known in the art.Further, instead of the live input streams and pre-encoded media assetarranged, as shown, different arrangements per the programming schedulemay be possible with respect to interstitial content items, such as thetargeted first non-programming content 208 and the customized firstprogramming content 210.

The insertion of the live input stream manifests, pre-encoded mediaasset manifests, the targeted first non-programming content 208 and thecustomized first programming content 210 may be done on-the-fly based ondynamic scheduling by the shared media session system 105 that generatesthe programming schedule. The insertion may be driven by real time ornear-real time content context analysis, user-selection on the pluralityof client devices 110, or driven by external data received from theexternal data source 120. The shared media session system 105 mayinclude a personalized manager (not shown) in association with thestream selection service (not shown) may be configured to insert liveinput streams, such as the first live input stream 202 and the secondlive input stream 206, or pre-stored media assets, such as the firstpre-encoded media asset 204, the targeted first non-programming content208 and the customized first programming content 210, in an existingdisparate live media output stream based on manipulation of a manifestthe existing disparate live media output stream, such as an existingchannel.

In accordance with an embodiment, each segment of the first set of videosegments 202 a, 202 b, 202 c, . . . , 202 n, the second set of videosegments 204 a, 204 b, 204 c, . . . , 204 n, and third set of videosegments 206 a, 206 b, 206 c, . . . , 206 n, may be further processed tobe stored at various quality levels, and content encryption modes forthe purposes of adaptive bitrate streaming and digital rightsmanagement, for example, the video segment 202 a may be stored in aplurality of quality levels, for example, high definition (HD), highdynamic range (HDR) video, or different quality levels in accordancewith specified pixel resolutions, bitrates, frame rates, and/or samplefrequencies. As each of the media content, such as 202 to 206, areencoded, segmented, and stored with the plurality of quality levels in amedia content master storage system. The media content may be re-used tocreate new channels, such as a new disparate live media output stream,without having to re-encode a selected live input stream or apre-encoded media asset when a new disparate live media output stream iscreated using the live input streams or a pre-encoded media asset.

For the sake of brevity, and with reference to FIG. 2 , there is shownan example of publishing first and updated (or alternate) disparate livemedia output streams based on dynamic insertion of targetednon-programming content and customized programming content by the DACIS103 of FIGS. 1A and 1B. It is to be understood that media packaging fordifferent delivery methods (such as analog terrestrial broadcast,digital terrestrial broadcast, direct-to-home satellite broadcast,cable, other Internet Protocol (IP)-based delivery methods, over-the-toptelevision (OTT)), different streaming protocols, or distributionsystem, may be different. The media content may be prepared to be viewedone or more of the plurality of client devices 110 based on at least thedesired delivery method, delivery conditions, content protectionrequirements, to satisfy operational and technical requirements, asneeded. The operational and technical requirements may include, but arenot limited to, media encoding, media segmentation, programming schedule(or manifest) creation or manipulation requirements, desired mediaencryption, and/or metadata signaling requirements. For example, incertain scenarios and for certain media content delivery methods,network bandwidth, network conditions, or device-type where mediacontent is to be consumed may not be variable or known in advance. Insuch a case, creating different quality levels for same media contentmay not be required. Further, based on different operational andtechnical requirements, publishing of disparate live media output streammay be different. The media content that is prepared and distributed mayinclude both the programming content, such as long-form presentations,short-form presentations, news or sporting events; and non-programmingcontent, such as paid advertisements, public service advertisements, orpromotional material.

FIG. 3A depicts a first flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

At 302, the shared media session may be defined based on one or morecharacteristics. In accordance with an embodiment, the shared mediasession system 105 may be configured to define the shared media sessionbased on one or more characteristics.

In accordance with an embodiment, the shared media session system 105may be configured to define the shared media session when the userinitiates creation of a new single-participant shared media session withthe shared media session system 105. In accordance with anotherembodiment, the shared media session system 105 may be configured todefine the shared media session when the user initiates creation of anew multi-participant shared media session with the shared media sessionsystem 105. In such embodiments, the user may be associated with thefirst client device 110 a. Various examples of the one or morecharacteristics may include, but are not limited to, a count of clientdevices that participate in the shared media session and interact with adisparate live media output stream, a selection of media content basedon which a disparate live media output stream manifest is generated, afirst flag that indicates the shared media session is discoverable bythe one or more second client devices, and a second flag that indicatesthe shared media session is to be recorded. In accordance with anembodiment, the selection of the media content may be performed by theuser associated with the first client device 110 a from a list ofexisting and referenced media content provided by the one or moreprocessors, or submitted by the user from an external storage.

At 304, the shared media session to be recorded may be determined basedon the second flag during the establishment of the shared media sessionor after the establishment of the shared media session. In accordancewith an embodiment, the shared media session system 105 may beconfigured to determine that the shared media session is to be recordedbased on the second flag during the establishment of the shared mediasession or after the establishment of the shared media session.Accordingly, in accordance with an embodiment, the shared media sessionsystem 105 may be configured to record the shared media session in arecorded client session database, such as the external storage system109. In accordance with another embodiment, the recording client device114 may be configured to record the shared media session in the recordedclient session database, such as the external storage system 109.

At 306, the shared media session may be established that includes adisparate live media output stream scheduled by the first client device110 a to start at a defined timestamp. In accordance with an embodiment,the shared media session system 105 may be configured to establish theshared media session that includes the disparate live media outputstream scheduled by the first client device 110 a to start at a definedtimestamp.

In accordance with an embodiment, the shared media session system 105may be configured to establish the shared media session as asingle-participant shared media session that comprises the first clientdevice 110 a and is initiated by the first client device 110 a. Inaccordance with an embodiment, the shared media session system 105 maybe configured to establish the shared media session as amulti-participant shared media session that comprises the plurality ofclient devices 110, and is initiated by the first client device 110 a.The shared media session may be established as the single-participantshared media session or the multi-participant shared media session basedon the type of request initiated by the user, as described at exemplaryoperation 302. In accordance with an embodiment, when the shared mediasession system 105 establishes the shared media session as thesingle-participant shared media session, the shared media session maynot have more than one participant, such as the first client device 110a.

In accordance with another embodiment, when the shared media sessionsystem 105 establishes the shared media session as the multi-participantshared media session, the shared media session may have the plurality ofparticipants, such as the plurality of client devices 110. In suchembodiment, the plurality of client devices 110 may be configured todiscover and join the distributed communication network 112, via thecorresponding peer-to-peer module similar to the first peer-to-peermodule 128. The shared media session may be advertised explicitly andselected by the first client device 110 a via an invitation or a shareduniversal resource locator. The shared media session may be furtheradvertised via an external advertisement service via a universalresource locator or an identifier. The shared media session may befurther advertised within context of a group of shared media sessionsdiscovered within the shared media session system 105.

When the plurality of client devices 110 joins the shared media sessionas participants, the first participant, for example, the first clientdevice 110 a, may be configured to establish the distributedcommunication network 112, via the first peer-to-peer module 128. Insuch a case, an identifier may be established for each participant andcommunicated to the shared media session system 105. The shared mediasession system 105 may be configured to receive and store the identifierfrom the first client device 110 a, and the identifier may be discoveredby the one or more second client devices 110 b, . . . , 110 n ₋₅ in theshared media session. In accordance with an embodiment, shared mediasession system 105 may be configured to receive and store theidentifiers from the remaining client devices 110 n ₋₅, . . . , 110 n,and the identifiers may be discovered by the one or more second clientdevices 110 b, . . . , 110 n in the shared media session

In accordance with an embodiment, a peer-to-peer network, for examplethe distributed communication network 112, may be established directlybetween client devices from the plurality of client devices 110. Eachclient device within the distributed communication network 112 may beidentified based on corresponding identifier. Once the distributedcommunication network 112 is established, event data and media may beshared between client devices from the plurality of client devices 110through the distributed communication network 112 based on correspondingidentifiers. The media may comprise audio data and video data. The audiodata may include, for example, at least an external audio media, anaudio recorded from a microphone, or an application-specific audioresource. The video data may include, for example, at least an externalvideo media, a video recorded from a participant camera, or anapplication-specific video resource. The event data may include, forexample, a first user interaction with the disparate live media outputstream that pauses video for the plurality of client devices 110, playsrewinds, fast-forward or seek media for the plurality of client devices110, or a second user interaction with another user. The event data mayfurther include, for example, a first broadcast notification of networkstate of the plurality of client devices 110 that is one of connected,disconnected or sending data. The event data may further include, forexample, a second broadcast notification of application state of theplurality of client devices 110 that is one of a muted audio, an invokedinteractive element, a completion of the invoked interactive element, achange in user application configuration, an update in playback state ofthe disparate live media output stream, a change in the playback stateof the disparate live media output stream, addition of new clientdevices or removal of existing one or more client devices from theplurality of client devices 110.

In accordance with an embodiment, wherein a schedule of the shared mediasession within the shared media session system 105 may indicate a startof the disparate live media output stream at a defined timestamp anddate. The defined timestamp and date may correspond with at least one ofa live event streamed in the disparate live media output stream orpre-encoded media assets streamed in the disparate live media outputstream. In accordance with an embodiment, the one or more second clientdevices 110 b, . . . , 110 n ₋₅ join or do not join the shared mediasession based on coordination with the defined timestamp and date in theschedule.

At 308, event data and media may be synchronized among the plurality ofclient devices 110 in the shared media session through the distributedcommunication network 112 based on one or more criteria. In accordancewith an embodiment, the shared media session system 105 may beconfigured to synchronize the event data and the media among theplurality of client devices 110 in the shared media session through thedistributed communication network 112 based on one or more criteria.

In accordance with an embodiment, when a user or a participant, forexample the first client device 110 a, in the distributed communicationnetwork 112, such as the peer-to-peer network, initiates the playback ofthe disparate live media output stream, via the media player 126, theevent data may be synchronized among the plurality of client devices 110in the shared media session through the distributed communicationnetwork 112. Event data may include a combination of real time and mediaplayhead time to maintain event sequence. Event data may haveapplication-specific actions that may be executed, such as,interactivity between peers, updating media playback state, changingmedia playback state, changing application state, and/or addition orremoval of peers.

In accordance with an embodiment, when a user or a participant, forexample the first client device 110 a of the plurality of client devices110, in the distributed communication network 112, such as thepeer-to-peer network, initiates the playback of the disparate live mediaoutput stream, via the media player 126, the media may be synchronizedamong the plurality of client devices 110 in the shared media sessionthrough the distributed communication network 112 based on the one ormore criteria. Examples of the one or more criteria may be defined basedon a level of synchronization accuracy corresponding to type of mediacontent in the disparate live media output stream, and view of sameposition in the disparate live media output stream by each client deviceconcurrently. The one or more criteria may be further defined based on acombination of one or more streaming protocols for example RTSP/RTP, andone or more control flow protocols utilized for synchronization, forexample RTSP/RTP with TS segments from HLS. The one or more criteria maybe further defined based on usage of a synchronizing client device ofthe plurality of client devices 110 to send playhead time relative to acalculated offset of time of another client device, application ofconstraints on a live window during playback of the disparate live mediaoutput stream and size of media segments in the disparate live mediaoutput stream such that a variability of different playback positions islimited to an accepted value, or a combination thereof.

At 310, the event data and media corresponding to the shared mediasession and previous shared media sessions may be transmitted to theexternal storage system 109 from the recording client device 114communicably coupled to the distributed communication network 112. Inaccordance with an embodiment, the external storage system 109 may beconfigured to receive the event data and media corresponding to theshared media session and previous shared media sessions from therecording client device 114 communicably coupled to the distributedcommunication network 112.

At 312, a persistent record of received event data and mediacorresponding to the shared media session and previous shared mediasessions may be generated until the shared media session is terminatedby at least one of the first client device 110 a or by abandonment ofthe distributed communication network 112 by the first client device 110a and by the one or more second client devices 110 b, . . . , 110 n ₋₅.The persistent records of the shared media session may be generated whenthe shared media session is flagged for recording, either during theshared media session creation or after the shared media sessioninitiation.

The distributed communication network 112 is established by the firstclient device 110 a in case of a single-participant shared mediasession, or the first client device 110 a from the plurality of clientdevices 110, in case of a multi-participant shared media session. Aclient identifier and a device address may be communicated to the sharedmedia session system 105 by the first client device 110 a. Thereafter,the recording client device 114 joins the distributed communicationnetwork 112 via the second peer-to-peer module 130, upon establishment,and then the event data and media exchanges originated from one or moreof the plurality of client devices 110 during the playback of thedisparate live media output stream is recorded by the recording clientdevice 114. In such case, the persistent record excludes the disparatelive media output stream selected for the playback in the shared mediasession. Each event data and media exchange may include a playhead timeof media playback, and real-time of event. Event data and mediaexchanges may then be synchronized with the playback of the disparatelive media output stream in the shared media session.

In case of multi-participant shared media session, the generatedpersistent record may comprise a persistent audio data exchanged betweenclient devices from the plurality of client devices 110 on thedistributed communication network 112, a persistent video data exchangedbetween client devices from the plurality of client devices 110 on thedistributed communication network 112, a persistent event data exchangedbetween client devices from the plurality of client devices 110 on thedistributed communication network 112, and/or time of the event data,audio data, and/or video data in accordance with real time or time ofthe disparate live media output stream. The persistent records of theshared media session may be coordinated with a start of shared mediasession, and/or according to number of participants in the peer-to-peernetwork.

In accordance with an embodiment, the shared media session system 105may be configured to persist the shared media session until the sharedmedia session is terminated by the first client device 110 a, in case ofsingle-participant shared media session. In accordance with anotherembodiment, the shared media session system 105 may be configured topersist the shared media session until the shared media session isterminated by the creating device, such as the first client device 110a, or all participants have abandoned the shared media session, in caseof multi-participant shared media session.

FIG. 3B depicts a second flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

At 320, the generated persistent record may be communicated to theexternal storage system 109. In accordance with an embodiment, the fileuploader 136 in the recording client device 114 may be configured tocommunicate the generated persistent record to the external storagesystem 109. The recorded event data and media exchanges may be uploadedto the external storage system 109, such as the recorded client sessiondatabase, where it may be further distributed and/or promoted. Recordedevent data and media exchanges, having been synchronized with playbackof the disparate live media output stream in the shared media session,may then be transcoded and distributed as a new media asset.

At 322, the persistent record may be retrieved from the external storagesystem 109. In accordance with an embodiment, the CPDS 107 may beconfigured to retrieve the persistent record from the external storagesystem 109.

At 324, the shared media session may be recreated at a future time basedon the event data and media in the retrieved persistent record. Inaccordance with an embodiment, the shared media session system 105, inconjunction with the CPDS 107, may be configured to recreate the sharedmedia session at a future time based on the event data and media in theretrieved persistent record.

At 326, the retrieved persistent record may be distributed through theCPDS 107 and/or the DACIS 103. In accordance with an embodiment, theCPDS 107 and/or DACIS 103 may be configured to distribute the retrievedpersistent record to the plurality of client devices 110 in thedistributed communication network 112 via the content delivery system122.

FIG. 3C depicts a third flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

At 330, an existing disparate live media output stream may be augmented.In accordance with an embodiment, a stream publishing engine (not shown)may be configured to augment the existing disparate live media outputstream. The augmentation may be based on the event data and mediacorresponding to the persistent record of the shared media session. Inaccordance with another embodiment, the DACIS 103 may be configured toaugment the existing disparate live media output stream. In such case,the augmentation may be based on dynamic ad/content insertion systemdesigned to construct and deliver targeted and/or personalized disparatelive media output streams.

At 332, a new disparate live media output stream may be generated. Inaccordance with an embodiment, a stream publishing engine in the sharedmedia session system 105 may be configured to generate the new disparatelive media output stream. The new disparate live media output stream maycomprise a plurality of distinct audio channels based on an audiointeraction of one of the plurality of client devices, and/or anapplication state of one of the plurality of client devices. The newdisparate live media output stream may further comprise a multiplexedaudio that may include an audio interaction of one of the plurality ofclient devices 110, an application state of one of the plurality ofclient devices 110, and/or an audio of the existing disparate live mediaoutput stream. Further, the recording client device 114 may beconfigured to record the event data and media exchanges between clientdevices from the plurality of client devices 110 during playback of theexisting disparate live media output stream. The persistent record mayexclude the existing disparate live media output stream selected for theshared media session playback. Each event data and media exchange mayinclude playhead time of the playback of the existing disparate livemedia output stream, and real-time of event. Further, the event data andmedia exchange may be synchronized with the playback of the existingdisparate live media output stream in the shared media session. Suchpersistent record of the event data and media exchanges may besynchronized with the playback of the existing disparate live mediaoutput stream of the shared media session and transcoded and distributedas the new disparate live media output stream. As described above, therecording client device 114 may be configured to communicate thegenerated persistent record to the external storage system 109 forfurther distribution and promotion. In accordance with an embodiment, ashared media session may be recreated at a future time based on theevent data and media in the persistent record. In accordance with anembodiment, the CPDS 107 may be configured to distribute the persistentrecord, retrieved from the external storage system 109, to the pluralityof client devices 110 in the distributed communication network 112 viathe content delivery system 122. In accordance with an embodiment, theCPDS 107 may be configured to transcode from the existing, persistentand stored version to a new format. Consequently, persistent records,comprising recorded event data and media exchanges, having beensynchronized with playback of the existing disparate live media outputstream in the shared media session, may be transcoded and distributed asa new disparate live media output stream. Upon the plurality of clientdevices 110 abandoning the distributed communication network 112, therecording client device 114 may be configured to cease the recording.Further, the recording client device 114 may alert the shared mediasession system 105 to close (or terminate) the shared media session.

FIG. 3D depicts a fourth flowchart illustrating exemplary operations ofmethods for establishing a shared media session for one or more clientdevices in the shared media session system of FIG. 1B, in accordancewith an exemplary embodiment of the disclosure.

At 340, the distributed communication network 112 associated with sharedmedia session established by shared media session system 105 may bejoined. In accordance with an embodiment, the recording client device114 may be configured to join the distributed communication network 112associated with shared media session established by shared media sessionsystem 105, via the second peer-to-peer module 130.

At 342, the event data and media exchanged between client devices fromthe plurality of client devices 110 on the distributed communicationnetwork 112 during playback of disparate live media output stream inshared media session may be recorded. In accordance with an embodiment,the recording client device 114 may be configured to record the eventdata and media exchanged between client devices from the plurality ofclient devices 110 on the distributed communication network 112 duringplayback of disparate live media output stream in shared media session.

At 344, the recorded event data and media may be transmitted to theexternal storage system 109. In accordance with an embodiment, therecording client device 114 may be configured to transmit the recordedevent data and media to the external storage system 109.

At 346, the recording of event data and media may be ceased based onabandonment of the distributed communication network 112 by theplurality of client devices 110. In accordance with an embodiment, therecording client device 114 may be configured to cease the recording ofevent data and media based on abandonment of the distributedcommunication network 112 by the plurality of client devices 110.

At 348, an alert may be generated for the shared media session system105 that establishes the shared media session to terminate shared mediasession. In accordance with an embodiment, the recording client device114 may be configured to generate an alert for the shared media sessionsystem 105 that establishes the shared media session to terminate sharedmedia session.

FIG. 4 is a conceptual diagram illustrating an example of a hardwareimplementation for a media packaging and distribution system 102employing a processing system for establishing a shared media sessionfor one or more client devices, in accordance with an exemplaryembodiment of the disclosure. Referring to FIG. 4 , the hardwareimplementation shown by a representation 400 for the media packaging anddistribution system 102 employs a processing system 402 for establishinga shared media session for one or more client devices, in accordancewith an exemplary embodiment of the disclosure, as described herein.

In some examples, the processing system 402 may comprise one or morehardware processors 404, a non-transitory computer-readable medium 406,a bus 408, a bus interface 410, and a transceiver 412. FIG. 4 furtherillustrates the DACIS 103, the shared media session system 105, the CPDS107, and the external storage system 109, as described in detail inFIGS. 1A and 1B.

The hardware processor 404 may be configured to manage the bus 408 andgeneral processing, including the execution of a set of instructionsstored on the non-transitory computer-readable medium 406. The set ofinstructions, when executed by the processor 404, causes the mediapackaging and distribution system 102 to execute the various functionsdescribed herein for any particular apparatus. The hardware processor404 may be implemented, based on a number of processor technologiesknown in the art. Examples of the hardware processor 404 may be aReduced Instruction Set Computing (RISC) processor, anApplication-Specific Integrated Circuit (ASIC) processor, a ComplexInstruction Set Computing (CISC) processor, and/or other processors orcontrol circuits.

The non-transitory computer-readable medium 406 may be used for storingdata that is manipulated by the processor 404 when executing the set ofinstructions. The data is stored for short periods or in the presence ofpower. The non-transitory computer-readable medium 406 may also beconfigured to store data for one or more of the DACIS 103, the sharedmedia session system 105, the CPDS 107, and the external storage system109.

The bus 408 is configured to link together various circuits. In thisexample, the media packaging and distribution system 102 employing theprocessing system 402 and the non-transitory computer-readable medium406 may be implemented with bus architecture, represented generally bybus 408. The bus 408 may include any number of interconnecting buses andbridges depending on the specific implementation of the media packagingand distribution system 102 and the overall design constraints. The businterface 410 may be configured to provide an interface between the bus408 and other circuits, such as, the transceiver 412, and externaldevices, such as the recording client device 114, the distributedcommunication network 112, the source device 118, the external datasource 120, and the plurality of client devices 110.

The transceiver 412 may be configured to provide a communication of themedia packaging and distribution system 102 with various otherapparatus, such as the Ad decisioning servers 106 a, . . . , 106 n, theplurality of client devices 110, the external data source 120, and thesource device 118, via the network 108. The transceiver 412 maycommunicate via wireless communication with networks, such as theInternet, the Intranet and/or a wireless network, such as a cellulartelephone network, a wireless local area network (WLAN) and/or ametropolitan area network (MAN). The wireless communication may use anyof a plurality of communication standards, protocols and technologies,such as Global System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), Long Term Evolution (LTE), wideband code divisionmultiple access (W-CDMA), code division multiple access (CDMA), timedivision multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi)(such as IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n),voice over Internet Protocol (VoIP), and/or Wi-MAX.

It should be recognized that, in some embodiments of the disclosure, oneor more components of FIG. 4 may include software whose correspondingcode may be executed by at least one processor, for across multipleprocessing environments. For example, the DACIS 103, the shared mediasession system 105, the CPDS 107, and the external storage system 109may include software that may be executed across a single or multipleprocessing environments.

In an aspect of the disclosure, the processor 404, the non-transitorycomputer-readable medium 406, or a combination of both may be configuredor otherwise specially programmed to execute the operations orfunctionality of the DACIS 103, the shared media session system 105, theCPDS 107, and the external storage system 109, or various othercomponents described herein, as described with respect to FIGS. 1A to1C.

Various embodiments of the disclosure comprise the media packaging anddistribution system 102 that may be configured to establish a sharedmedia session for one or more client devices, such as the plurality ofclient devices 110. The media packaging and distribution system 102 maycomprise, for example, the DACIS 103, the shared media session system105, the CPDS 107, and the external storage system 109. In accordancewith an embodiment, one or more processors in the shared media sessionsystem 105 may be configured to establish a shared media session. Theshared media session may include a disparate live media output streamscheduled by the first client device 110 a to start at a definedtimestamp. The disparate live media output stream may be played back onone of the first client device 110 a or the plurality of client devices110 that comprises the first client device 110 a and one or more secondclient devices 110 b, . . . , 110 n. The plurality of client devices 110may join the shared media session through the distributed communicationnetwork 112. During the shared media session, event data and media amongthe plurality of client devices 110 in the shared media session may besynchronized through the distributed communication network 112 based onone or more criteria. The one or more processors in the shared mediasession system 105 may be further configured to receive the event dataand media corresponding to the shared media session and previous sharedmedia sessions from the recording client device 114 communicably coupledto the distributed communication network 112. The one or more processorsin the shared media session system 105 may be further configured togenerate a persistent record of received event data and mediacorresponding to the shared media session and previous shared mediasessions until the shared media session is terminated by at least one ofthe first client device 110 a or by abandonment of the distributedcommunication network 112 by the first client device 110 a and by theone or more second client devices 110 b, . . . , 110 n.

In accordance with an embodiment, the shared media session system 105may be configured to define the shared media session based on one ormore characteristics. The one or more characteristics may comprise acount of client devices 110 that participate in the shared media sessionand interact with the disparate live media output stream, a selection ofmedia content based on which a disparate live media output streammanifest is generated, a first flag that indicates the shared mediasession is discoverable by the one or more second client devices 110 b,. . . , 110 n via the system, and a second flag that indicates theshared media session is to be recorded. In accordance with anembodiment, the media content may be selected by the user associatedwith the first client device 110 a from a list of existing andreferenced media content provided by the one or more processors, orsubmitted by the user from an external source. The one or moreprocessors in the shared media session system 105 may be furtherconfigured to determine that the shared media session is to be recordedbased on the second flag during the establishment of the shared mediasession or after the establishment of the shared media session.

In accordance with an embodiment, the distributed communication network112 may be established by the first client device 110 a. A clientidentifier and device address may be communicated to the one or moreprocessors in the shared media session system 105 by the first clientdevice 110 a. In accordance with another embodiment, the establisheddistributed communication network 112 may be joined by the recordingclient device 114, via the second peer-to-peer module 130. The eventdata and the media exchanges between client devices from the pluralityof client devices 110 during the playback of the disparate live mediaoutput stream may be recorded by the recording client device 114.

In accordance with an embodiment, the persistent record may exclude thedisparate live media output stream selected for the playback in theshared media session. Each event data and media exchange may includeplayhead time of the playback of the disparate live media output stream,and real-time of an event. The event data and media exchange may besynchronized with the playback of the disparate live media output streamin the shared media session. The one or more processors in the sharedmedia session system 105 may be configured to persist the shared mediasession until the shared media session is terminated by the first clientdevice 110 a.

In accordance with an embodiment, the shared media session is asingle-participant shared media session that comprises the first clientdevice 110 a and is initiated by the first client device 110 a. Inaccordance with another embodiment, the shared media session is amulti-participant shared media session that comprises the plurality ofclient devices 110, and is initiated by the first client device 110 a.The distributed communication network 112 that comprises the pluralityof client devices 110 may correspond to a peer-to-peer network. Theplurality of client devices 110 may be configured to discover and jointhe distributed communication network 112 by the shared media session,via the corresponding first peer-to-peer module 128. The shared mediasession may be advertised explicitly and selected by the first clientdevice 110 a via an invitation or a shared universal resource locator,via an external advertisement service via a universal resource locatoror an identifier, or within context of a group of shared media sessionsdiscovered within the system.

In accordance with an embodiment, the distributed communication network112 may be established by the first client device 110 a in an instancein which the first client device 110 a is a first participant. Anidentifier may be established for each participant. The one or moreprocessors in the shared media session system 105 may be configured toreceive and store an identifier from the first client device 110 a. Theidentifier may be discovered by the one or more second client devices110 b, . . . , 110 n in the shared media session. The one or moreprocessors in the shared media session system 105 may be furtherconfigured to receive and store identifiers for remaining client devicesof the shared media session. The identifier may be discovered by the oneor more second client devices 110 b, . . . , 110 c in the shared mediasession. The distributed communication network 112 may be establisheddirectly between client devices from the plurality of client devices110. Each client device within the distributed communication network 112may be identified based on corresponding identifier. The event data andmedia may be shared between client devices from the plurality of clientdevices 110 through the distributed communication network 112. Inaccordance with an embodiment, the media may comprise audio data andvideo data. The audio data may include at least an external audio media,an audio recorded from a microphone, or an application-specific audioresource. The video data may include at least an external video media, avideo recorded from a participant camera, or an application-specificvideo resource. The event data may include a first user interaction withdisparate live media output stream that pauses video for the pluralityof client devices 110, plays rewinds, fast-forward or seek media for theplurality of client devices 110, or a second user interaction withanother user. The event data may further include a first broadcastnotification of network state of the plurality of client devices 110that is one of connected, disconnected or sending data, or a secondbroadcast notification of application state of the plurality of clientdevices 110 that is one of a muted audio, an invoked interactiveelement, a completion of the invoked interactive element, a change inuser application configuration, an update in playback state of thedisparate live media output stream, a change in the playback state ofthe disparate live media output stream, addition of new client devicesor removal of existing client devices. The event data may furtherinclude a combination of real time and media playhead time to maintainevent sequence.

In accordance with an embodiment, a schedule of the shared media sessionwithin the system indicates a start of the disparate live media outputstream at the defined timestamp and date. The defined timestamp and datemay correspond with at least one of a live event streamed in thedisparate live media output stream or pre-encoded media assets streamedin the disparate live media output stream. The one or more second clientdevices 110 b, . . . , 110 n may join or do not join the shared mediasession based on coordination with the defined timestamp and date in theschedule. In accordance with an embodiment, the one or more processorsin the shared media session system 105 may be configured to store thepersistent record corresponding to the shared media session. The one ormore criteria may be defined based on a level of synchronizationaccuracy corresponding to type of media content in the disparate livemedia output stream, view of same position in the disparate live mediaoutput stream by each client device concurrently, a combination of oneor more streaming protocols and one or more control flow protocolsutilized for synchronization, usage of a synchronizing client device ofthe plurality of client devices 110 to send playhead time relative to acalculated offset of time of another client device, application ofconstraints on a live window during playback of the disparate live mediaoutput stream and size of media segments in the disparate live mediaoutput stream such that a variability of different playback positions islimited to an accepted value, or a combination thereof. In accordancewith an embodiment, the generated persistent record may comprise apersistent audio data exchanged between client devices from theplurality of client devices 110 on the distributed communication network112, a persistent video data exchanged between client devices from theplurality of client devices 110 on the distributed communication network112, a persistent event data exchanged between client devices from theplurality of client devices 110 on the distributed communication network112, and/or time of the event data, audio data, and/or video data inaccordance with real time or time of the disparate live media outputstream.

In accordance with an embodiment, the one or more processors may befurther configured to communicate the generated persistent record to theexternal storage system 109, retrieve the persistent record from theexternal storage system 109, recreate the shared media session at afuture time based on the event data and media in the retrievedpersistent record, and distribute the retrieved persistent recordthrough the CPDS 107. The CPDS 107 may be configured to transcode froman existing, persistent and stored record from a first encoding formatto a second encoding format. The one or more processors may be furtherconfigured to coordinate the recording of the shared media session withstart of shared media session or according to number of the plurality ofclient devices 110 in the distributed communication network 112. The oneor more processors may be further configured to define a contentidentifier for the shared media session, and receive a request from athird client device for the persistent record of the received event dataand media corresponding to the shared media session and previous sharedmedia sessions. The third client device may be one of the distributedcommunication network 112 or external to the distributed communicationnetwork 112.

In accordance with an embodiment, the one or more processors may befurther configured to augment an existing disparate live media outputstream to generate a new disparate live media output stream. Theaugmentation may be based on the event data and media corresponding tothe persistent record of the shared media session. The new disparatelive media output stream may comprises a plurality of distinct audiochannels based on an audio interaction of one of the plurality of clientdevices 110, and/or an application state of one of the plurality ofclient devices 110. The new disparate live media output stream maycomprise a multiplexed audio that includes an audio interaction of oneof the plurality of client devices 110, or an application state of oneof the plurality of client devices 110, and/or an audio of the existingdisparate live media output stream. The recording client device 114 mayrecord the event data and media exchanges between client devices of theplurality of client devices 110 during playback of the existingdisparate live media output stream.

The persistent record may exclude the existing disparate live mediaoutput stream selected for the shared media session playback. Each eventdata and media exchange may include playhead time of the playback of thedisparate live media output stream, and real-time of event. The eventdata and media exchange may be synchronized with the playback of thedisparate live media output stream in the shared media session. Thepersistent record of the event data and media exchanges may besynchronized with the playback of the existing disparate live mediaoutput stream of the shared media session and transcoded and distributedas the new disparate live media output stream.

In accordance with an embodiment, the one or more processors in therecording client device 114 may be configured to join the distributedcommunication network 112 associated with the shared media sessionestablished by the shared media session system 105, via the secondpeer-to-peer module 130. A disparate live media output stream may beplayed back on one of the first client device 110 a or the plurality ofclient devices 110 that comprises the first client device 110 a and oneor more second client devices 110 b, . . . , 110 n. The event data andmedia among the plurality of client devices 110 may be synchronized inthe shared media session through the distributed communication network112 based on one or more criteria. The one or more processors in therecording client device 114 may be further configured to record theevent data and media exchanged between client devices from the pluralityof client devices 110 on the distributed communication network 112during the playback of the disparate live media output stream in theshared media session. The one or more processors in the recording clientdevice 114 may be further configured to transmit the recorded event dataand media to the external storage system 109. The one or more processorsin the recording client device 114 may be further configured to ceasethe recording of the event data and media based on abandonment of thedistributed communication network 112 by the plurality of client devices110. The one or more processors in the recording client device 114 maybe further configured to generate an alert for the shared media sessionsystem 105 that establishes the shared media session to terminate theshared media session. The user associated with the first client device110 a may initiate an establishment of a single-participant or amulti-participant shared media session. The user may further schedulethe disparate live media output stream and initiates the playback of thedisparate live media output stream.

Various embodiments of the disclosure may provide a computer-readablemedium, such as the non-transitory computer-readable medium 406, havingstored thereon, computer implemented instruction that when executed bythe processor 404 causes the media packaging and distribution system 102to execute operations for establishing a shared media session for one ormore client devices. In accordance with an embodiment, the processor 404causes the media packaging and distribution system 102 to executeoperations to establish a shared media session. The shared media sessionmay include a disparate live media output stream scheduled by the firstclient device 110 a to start at a defined timestamp. The disparate livemedia output stream may be played back on one of the first client device110 a or the plurality of client devices 110 that comprises the firstclient device 110 a and one or more second client devices 110 b, . . . ,110 n. The plurality of client devices 110 may join the shared mediasession through the distributed communication network 112, via thecorresponding first peer-to-peer module 128. The processor 404 furthercauses the media packaging and distribution system 102 to executeoperations to synchronize event data and media among the plurality ofclient devices 110 in the shared media session through the distributedcommunication network 112 based on one or more criteria. The processor404 further causes the media packaging and distribution system 102 toexecute operations to receive the event data and media corresponding tothe shared media session and previous shared media sessions from therecording client device 114 communicably coupled to the distributedcommunication network 112. The processor 404 further causes the mediapackaging and distribution system 102 to execute operations to generatea persistent record of received event data and media corresponding tothe shared media session and previous shared media sessions until theshared media session is terminated by at least one of the first clientdevice 110 a or by abandonment of the distributed communication network112 by the first client device 110 a and by the one or more secondclient devices 110 b, . . . , 110 n.

Modern streaming protocols may also support delivery of disparate livemedia output stream to multiple client devices. Accordingly, shortcontent media segments, facilitated by such modern streaming protocols,are made available as soon as they are created. In some streamingprotocols, each new segment is added to the manifest of the disparatelive media output stream while in others the media player at the clientdevices are provided necessary information to calculate the next livesegment. In the latter case, a signal in the disparate live media outputstream itself is used to inform the media player when the media playershould reinspect the manifest for a change in content (media or other)in the disparate live media output stream. The manifest and/or the mediasegment may further include additional information to facilitate themedia player to transition smoothly between media content from differentsources. This may be used for creating a playlist of multiple disparatelive media output streams, or for interrupting a disparate live mediaoutput stream with advertising and then resuming the disparate livemedia output stream.

Because the disparate live media output stream itself does not need tobe processed beyond the initial creation of the live input streams andpre-encoded media assets prepared for web distribution, it is extremelyinexpensive to provide such branches. It may be based solely on the costto manipulate the manifests that provide execution instructions for themedia players in the client devices. Further, targeted ad insertion on aper client basis may also be supported through the insertion of ad tagsin the generated disparate live media output stream manifest and mayfurther leverage the processing power of the individual client devicesto insert targeted channel graphics and overlay advertisements andpromotions.

The shared media session system 105 in the media packaging anddistribution system 102 may be configured to construct shared mediasessions and facilitate participants of a given shared media sessionwith constructing a peer-to-peer network between participants. As anextension to the CPDS 107, the media packaging and distribution system102 may be configured to provide additional capabilities that may allowan explicit channel creation by a user for a single view, an explicitchannel creation by a user for group viewing and interactions, and anexplicit channel creation by a user for group viewing with accuratesynchronization and extended interactivity.

For example, in accordance with the explicit channel creation by theuser for the single view, the user may want to play all the vacationseries of a thanksgiving movie back-to-back. In such case, the user mayschedule the vacation series, play the vacation series, and view thevacation series on a channel. The channel may be scheduled in such amanner that manifests, queues, graphical treatment (for exampleoverlays), promotional content in the beginning, ad breaks or no adbreaks in the middle may be maintained by the media packaging anddistribution system 102.

In another example, in accordance with the explicit channel creation bythe user for group viewing, the user may be schedule the channel andjoined by other viewers at the same location to watch the disparate livemedia output stream being played on the client device associated withthe user. However, other viewers are disconnected viewers and do notactively participate in the session corresponding to the channelcreation.

In another example, in accordance with the explicit channel creation bythe user for group viewing, for example a sporting event, with accuratesynchronization and extended interactivity, the user may schedule thechannel and also invite the other viewers to watch the same framesimultaneously. However, in certain cases, for example the Oscars event,the synchronization may not be tightly coupled but extendedinteractivity is provided between the user and the other viewers. Inboth the embodiments, the same disparate live media output stream may bedisplayed on the devices associated with the other viewers. Further,during watching the same disparate live media output stream, the usermay have an option to interact with the other viewers.

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (for example, hardware) and any softwareand/or firmware (“code”) which may configure the hardware, be executedby the hardware, and/or otherwise be associated with the hardware. Asused herein, for example, a particular processor and memory may comprisea first “circuit” when executing first one or more lines of code and maycomprise a second “circuit” when executing second one or more lines ofcode. As utilized herein, “and/or” means any one or more of the items inthe list joined by “and/or”. As an example, “x and/or y” means anyelement of the three-element set {(x), (y), (x, y)}. As another example,“x, y, and/or z” means any element of the seven-element set {(x), (y),(z), (x, y), (x, z), (y, z), (x, y, z)}. As utilized herein, the term“exemplary” means serving as a non-limiting example, instance, orillustration. As utilized herein, the terms “e.g.,” and “for example”set off lists of one or more non-limiting examples, instances, orillustrations. As utilized herein, circuitry is “operable” to perform afunction whenever the circuitry comprises the necessary hardware and/orcode (if any is necessary) to perform the function, regardless ofwhether performance of the function is disabled, or not enabled, by someuser-configurable setting.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of embodiments ofthe disclosure. As used herein, the singular forms “a”, “an” and “the”are intended to include the plural forms as well, unless the contextclearly indicates otherwise. It will be further understood that theterms “comprises”, “comprising”, “includes” and/or “including”, whenused herein, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

Further, many embodiments are described in terms of sequences of actionsto be performed by, for example, elements of a computing device. It willbe recognized that various actions described herein can be performed byspecific circuits (e.g., application specific integrated circuits(ASICs)), by program instructions being executed by one or moreprocessors, or by a combination of both. Additionally, these sequencesof actions described herein can be considered to be embodied entirelywithin any non-transitory form of computer readable storage mediumhaving stored therein a corresponding set of computer instructions thatupon execution would cause an associated processor to perform thefunctionality described herein. Thus, the various aspects of thedisclosure may be embodied in a number of different forms, which havebeen contemplated to be within the scope of the claimed subject matter.In addition, for each of the embodiments described herein, thecorresponding form of any such embodiments may be described herein as,for example, “logic configured to” perform the described action.

Another embodiment of the disclosure may provide a non-transitorymachine and/or computer readable storage and/or media, having storedthereon, a machine code and/or a computer program having at least onecode section executable by a machine and/or a computer, thereby causingthe machine and/or computer to perform the steps as described herein forestablishing a shared media session for one or more client devices.

The present disclosure may also be embedded in a computer programproduct, which comprises all the features enabling the implementation ofthe methods described herein, and which when loaded in a computer systemis able to carry out these methods. Computer program in the presentcontext means any expression, in any language, code or notation, eitherstatically or dynamically defined, of a set of instructions intended tocause a system having an information processing capability to perform aparticular function either directly or after either or both of thefollowing: a) conversion to another language, code or notation; b)reproduction in a different material form.

Further, those of skill in the art will appreciate that the variousillustrative logical blocks, modules, circuits, algorithms, and/or stepsdescribed in connection with the embodiments disclosed herein may beimplemented as electronic hardware, computer software, firmware, orcombinations thereof. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

The methods, sequences and/or algorithms described in connection withthe embodiments disclosed herein may be embodied directly in firmware,hardware, in a software module executed by a processor, or in acombination thereof. A software module may reside in RAM memory, flashmemory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk,physical and/or virtual disk, a removable disk, a CD-ROM, virtualizedsystem or device such as a virtual servers or container, or any otherform of storage medium known in the art. An exemplary storage medium iscommunicatively coupled to the processor (including logic/code executingin the processor) such that the processor can read information from, andwrite information to, the storage medium. In the alternative, thestorage medium may be integral to the processor.

While the present disclosure has been described with reference tocertain embodiments, it will be noted understood by, for example, thoseskilled in the art that various changes and modifications could be madeand equivalents may be substituted without departing from the scope ofthe present disclosure as defined, for example, in the appended claims.In addition, many modifications may be made to adapt a particularsituation or material to the teachings of the present disclosure withoutdeparting from its scope. The functions, steps and/or actions of themethod claims in accordance with the embodiments of the disclosuredescribed herein need not be performed in any particular order.Furthermore, although elements of the disclosure may be described orclaimed in the singular, the plural is contemplated unless limitation tothe singular is explicitly stated. Therefore, it is intended that thepresent disclosure not be limited to the particular embodimentdisclosed, but that the present disclosure will include all embodimentsfalling within the scope of the appended claims.

What is claimed is:
 1. A system, comprising: memory for storinginstructions; and a processor configured to execute the instructions,and based on the executed instructions, the processor is furtherconfigured to: generate a persistent record of event data and mediacorresponding to a shared media session and previous shared mediasessions until the shared media session is terminated by at least one ofa first client device or by abandonment of a distributed communicationnetwork by the first client device and by second client devices; andgenerate a new disparate live media output stream with multiple distinctchannels based on an augmentation of an existing disparate live mediaoutput stream in the shared media session, wherein the persistent recordof the event data and media is synchronized with a playback of theexisting disparate live media output stream in the shared media sessionas the new disparate live media output stream with the multiple distinctchannels.
 2. The system according to claim 1, wherein the processor isfurther configured to: establish the shared media session that includesthe existing disparate live media output stream scheduled by the firstclient device to start at a defined timestamp, wherein the shared mediasession is one of a single-participant shared media session or amulti-participant shared media session, wherein the existing disparatelive media output stream is played back on one of the first clientdevice or a plurality of client devices that comprises the first clientdevice and the second client devices, wherein the plurality of clientdevices join the shared media session through the distributedcommunication network, wherein the event data includes a first userinteraction with the existing disparate live media output stream thatpauses video for the plurality of client devices, plays rewinds,fast-forward or seek media for the plurality of client devices, or asecond user interaction with another user, wherein the event datafurther includes a first broadcast notification of network state of theplurality of client devices that is one of connected, disconnected orsending data, or a second broadcast notification of application state ofthe plurality of client devices that is one of a muted audio, an invokedinteractive element, a completion of the invoked interactive element, achange in user application configuration, an update in a playback stateof the existing disparate live media output stream, a change in theplayback state of the existing disparate live media output stream,addition of new client devices or removal of existing client devices,and wherein the event data further includes a combination of real timeand media playhead time to maintain event sequence; synchronize theevent data and media among the plurality of client devices in the sharedmedia session through the distributed communication network based on acriteria, wherein the criteria is defined based on a level ofsynchronization accuracy corresponding to type of media content in theexisting disparate live media output stream, view of same position inthe existing disparate live media output stream by each client deviceconcurrently, a combination of streaming protocols and control flowprotocols utilized for synchronization, usage of a synchronizing clientdevice of the plurality of client devices to send playhead time relativeto a calculated offset of time of another client device, application ofconstraints on a live window during the playback of the existingdisparate live media output stream and size of media segments in theexisting disparate live media output stream such that a variability ofdifferent playback positions is limited to an accepted value, or acombination thereof; and coordinate a recording of the shared mediasession with start of the shared media session or according to number ofthe plurality of client devices in the distributed communicationnetwork.
 3. The system according to claim 2, wherein the processor isfurther configured to: define the shared media session based on aplurality of characteristics, wherein the plurality of characteristicscomprise a count of client devices that participate in the shared mediasession and interact with the existing disparate live media outputstream, a selection of the media content based on which a disparate livemedia output stream manifest is generated, a first flag that indicatesthe shared media session is discoverable by the second client devicesvia the system, and a second flag that indicates the shared mediasession is to be recorded, and wherein the media content is selected bythe user associated with the first client device from a list of existingand referenced media content provided by the processor, or submitted bythe user from an external source; and determine that the shared mediasession is to be recorded based on the second flag during theestablishment of the shared media session or after the establishment ofthe shared media session.
 4. The system according to claim 1, whereinthe persistent record excludes a disparate live media output streamselected for the playback in the shared media session.
 5. The systemaccording to claim 2, wherein the shared media session is advertisedexplicitly and selected by the first client device via an invitation ora shared universal resource locator, via an external advertisementservice via a universal resource locator or an identifier, or withincontext of a group of shared media sessions discovered within thesystem.
 6. The system according to claim 2, wherein the distributedcommunication network is established by the first client device in aninstance in which the first client device is a first participant, andwherein an identifier is established for each participant.
 7. The systemaccording to claim 6, wherein the processor is further configured toreceive and store a first identifier from the first client device,wherein the first identifier is discovered by the second client devicesin the shared media session, wherein the distributed communicationnetwork is established directly between the plurality of client devices,wherein each client device within the distributed communication networkis identified based on corresponding identifier, and wherein the eventdata and media is shared between the plurality of client devices throughthe distributed communication network.
 8. The system according to claim6, wherein the processor is further configured to store identifiersreceived for remaining client devices of the shared media session, andwherein the identifiers are discovered by the second client devices inthe shared media session.
 9. The system according to claim 2, wherein aschedule of the shared media session within the system indicates a startof the existing disparate live media output stream at the definedtimestamp and a defined date, wherein the defined timestamp and thedefined date correspond to at least one of a live event streamed in theexisting disparate live media output stream or pre-encoded media assetsstreamed in the existing disparate live media output stream, wherein thesecond client devices join or do not join the shared media session basedon coordination with the defined timestamp and the defined date in theschedule, and wherein the persistent record comprises a persistent audiodata exchanged between the plurality of client devices on thedistributed communication network, a persistent video data exchangedbetween the plurality of client devices on the distributed communicationnetwork, a persistent event data exchanged between the plurality ofclient devices on the distributed communication network, and/or time ofthe event data, audio data, and/or video data based on real time or timeof the existing disparate live media output stream.
 10. The systemaccording to claim 1, wherein the processor is further configured to:communicate the persistent record to an external storage system;retrieve the persistent record from the external storage system;recreate the shared media session at a future time based on the eventdata and media in the retrieved persistent record; and distribute theretrieved persistent record through a content packaging and distributionsystem that transcodes the persistent record from a first encodingformat to a second encoding format.
 11. The system according to claim 1,wherein the processor is further configured to: define a contentidentifier for the shared media session; and receive a request from athird client device for the persistent record of the event data andmedia corresponding to the shared media session and the previous sharedmedia sessions, wherein the third client device is one of in thedistributed communication network or external to the distributedcommunication network.
 12. The system according to claim 2, wherein theaugmentation is further based on the event data and media correspondingto the persistent record of the shared media session, wherein the newdisparate live media output stream comprises one of a plurality ofdistinct audio channels or a multiplexed audio, wherein the plurality ofdistinct audio channels is based on an audio interaction of one of theplurality of client devices, and/or an application state of one of theplurality of client devices, and wherein the multiplexed audio includesthe audio interaction of the one of the plurality of client devices, orthe application state of the one of the plurality of client devices,and/or an audio of the existing disparate live media output stream. 13.The system according to claim 2, wherein a plurality of exchanges of theevent data and media between the plurality of client devices is recordedby a recording client device during the playback of the existingdisparate live media output stream, wherein the persistent recordexcludes the existing disparate live media output stream selected forthe playback, wherein each exchange of the event data and media includesplayhead time of the playback of the existing disparate live mediaoutput stream, and real-time of event, and is synchronized with theplayback of the existing disparate live media output stream in theshared media session, and wherein the persistent record of the eventdata and media exchanges are synchronized with the playback of theexisting disparate live media output stream of the shared media sessionand transcoded and distributed as the new disparate live media outputstream.
 14. A method, comprising: generating, by a processor, apersistent record of event data and media corresponding to a sharedmedia session and previous shared media sessions until the shared mediasession is terminated by at least one of a first client device or byabandonment of a distributed communication network by the first clientdevice and by second client devices; and generating, by the processor, anew disparate live media output stream with multiple distinct channelsbased on an augmentation of an existing disparate live media outputstream in the shared media session, wherein the persistent record of theevent data and media is synchronized with a playback of the existingdisparate live media output stream in the shared media session as thenew disparate live media output stream with the multiple distinctchannels.
 15. The method according to claim 14, further comprising:establishing, by the processor, the shared media session that includesthe existing disparate live media output stream scheduled by the firstclient device to start at a defined timestamp, wherein the shared mediasession is one of a single-participant shared media session or amulti-participant shared media session, wherein the existing disparatelive media output stream is played back on one of the first clientdevice or a plurality of client devices that comprises the first clientdevice and the second client devices, wherein the plurality of clientdevices join the shared media session through the distributedcommunication network, wherein the event data includes a first userinteraction with the existing disparate live media output stream thatpauses video for the plurality of client devices, plays rewinds,fast-forward or seek media for the plurality of client devices, or asecond user interaction with another user, wherein the event datafurther includes a first broadcast notification of network state of theplurality of client devices that is one of connected, disconnected orsending data, or a second broadcast notification of application state ofthe plurality of client devices that is one of a muted audio, an invokedinteractive element, a completion of the invoked interactive element, achange in user application configuration, an update in a playback stateof the existing disparate live media output stream, a change in theplayback state of the existing disparate live media output stream,addition of new client devices or removal of existing client devices;synchronizing, by the processor, the event data and media among theplurality of client devices in the shared media session through thedistributed communication network based on criteria, wherein criteria isdefined based on a level of synchronization accuracy corresponding totype of media content in the existing disparate live media outputstream, view of same position in the existing disparate live mediaoutput stream by each client device concurrently, a combination ofstreaming protocols and control flow protocols utilized forsynchronization, usage of a synchronizing client device of the pluralityof client devices to send playhead time relative to a calculated offsetof time of another client device, application of constraints on a livewindow during the playback of the existing disparate live media outputstream and size of media segments in the existing disparate live mediaoutput stream such that a variability of different playback positions islimited to an accepted value, or a combination thereof; andcoordinating, by the processor, a recording of the shared media sessionwith start of shared media session or according to number of theplurality of client devices in the distributed communication network.16. The method according to claim 15, further comprising: defining, bythe processor, the shared media session based on a plurality ofcharacteristics, wherein the plurality of characteristics comprise acount of client devices that participate in the shared media session andinteract with the existing disparate live media output stream, aselection of the media content based on which a disparate live mediaoutput stream manifest is generated, a first flag that indicates theshared media session is discoverable by the second client devices, and asecond flag that indicates the shared media session is to be recorded,and wherein the media content is selected by the user associated withthe first client device from a list of existing and referenced mediacontent provided by the processor, or submitted by the user from anexternal source; and determining, by the processor, that the sharedmedia session is to be recorded based on the second flag during theestablishment of the shared media session or after the establishment ofthe shared media session.
 17. The method according to claim 14, furthercomprising: communicating, by the processor, the persistent record to anexternal storage system; retrieving, by the processor, the persistentrecord from the external storage system; recreating, by the processor,the shared media session at a future time based on the event data andmedia in the retrieved persistent record; and distributing, by theprocessor, the retrieved persistent record through a content packagingand distribution system that transcodes the persistent record from afirst encoding format to a second encoding format.
 18. The methodaccording to claim 14, defining, by the processor, a content identifierfor the shared media session; and receiving, by the processor, a requestfrom a third client device for the persistent record of the event dataand media corresponding to the shared media session and the previousshared media sessions, wherein the third client device is one of in thedistributed communication network or external to the distributedcommunication network.
 19. The method according to claim 15, wherein theaugmentation is further based on the event data and media correspondingto the persistent record of the shared media session, wherein the newdisparate live media output stream comprises one of a plurality ofdistinct audio channels or a multiplexed audio, wherein the plurality ofdistinct audio channels is based on an audio interaction of one of theplurality of client devices, and/or an application state of one of theplurality of client devices, and wherein the multiplexed audio includesthe audio interaction of the one of the plurality of client devices, orthe application state of the one of the plurality of client devices,and/or an audio of the existing disparate live media output stream. 20.A non-transitory computer readable medium, having stored thereon,computer executable code, which when executed by a processor, cause theprocessor to execute operations, the operations comprising: generating apersistent record of event data and media corresponding to a sharedmedia session and previous shared media sessions until the shared mediasession is terminated by at least one of a first client device or byabandonment of a distributed communication network by the first clientdevice and by second client devices; and generating a new disparate livemedia output stream with multiple distinct channels based onaugmentation of an existing disparate live media output stream in theshared media session, wherein the persistent record of the event dataand media is synchronized with a playback of the existing disparate livemedia output stream in the shared media session as the new disparatelive media output stream with the multiple distinct channels.
 21. Thesystem according to claim 1, wherein the processor is further configuredto provide additional capabilities to allow an explicit channel creationby a user for a single view.
 22. The system according to claim 1,wherein the processor is further configured to provide additionalcapabilities to allow an explicit channel creation by a user for a groupviewing and interactions.
 23. The system according to claim 1, whereinthe processor is further configured to provide additional capabilitiesto allow an explicit channel creation by a user for a group viewing withaccurate synchronization and extended interactivity.